Go-Live Checklist

Use this checklist to prepare your Euclid integration for production.

This is primarily for developers integrating directly with the Euclid APIs or signing transactions on-chain. If you're using a wrapper SDK, widget, or partner platform, many of these items may already be handled for you.

Environment & Configuration

• Confirm you're using the production API endpoint: https://api.euclidprotocol.com
• Remove or replace any testnet-specific addresses, contracts, or chain UIDs
• Set your `timeout` values appropriately (e.g. 60, 180) for production latency
• Use live wallet addresses and verify all chain configurations

API Keys & Authentication

• Create a production API key in the Developer Portal
• Store API keys securely using secrets managers or environment variables
• Confirm no API keys are hardcoded or checked into version control
• Rotate keys if they were exposed or used in development

Transaction Flow

• Simulate trades before submitting them with real assets
• Confirm `slippage` values are reasonable for your asset pairs
• Handle swap rejections or failures gracefully
• Ensure you’re only submitting transactions with confirmed `swap_path` or routes
• Broadcast only fully signed messages to the appropriate chain

Error Handling & Edge Cases

• Handle all API response types (4xx, 5xx)
• Implement retry logic with backoff where needed
• Validate all inputs client- and server-side
• Ensure duplicate requests are idempotent

Logging & Monitoring

• Log all outgoing API requests (excluding sensitive data)
• Log all error responses for debugging
• Set up error alerting or Sentry-style tracking
• Sanitize logs to avoid leaking PII or private keys

Security

• Ensure all wallet signing is done through trusted sources (e.g. MetaMask, Keplr)
• Avoid exposing private keys in any frontend context
• Ensure transactions are chain-specific and cannot be replayed elsewhere

Production Checklist

• Review all contracts, addresses, and tokens used
• Test every step in production with a small real trade
• Review fallback and error pages for user experience

Stay Updated

• Subscribe to API announcements or follow the changelog
• Monitor for new token integrations or protocol changes

Final Tip

We recommend having at least one non-developer test the full end-to-end flow before going live to ensure usability.